As HAProxy is running chrooted by default, we rely on an additional syslog
socket created by rsyslog inside the chroot for logging. As this socket cannot
trigger syslog activation, we explicitly order HAProxy after rsyslog.service.
Note that we are not using syslog.service here, since the additional socket is
rsyslog-specific.
Forwarded: no
Last-Update: 2017-12-01
Gbp-Pq: Name haproxy.service-start-after-syslog.patch
Vincent Bernat [Fri, 27 Sep 2019 17:14:12 +0000 (18:14 +0100)]
haproxy (2.0.7-1) unstable; urgency=medium
* New upstream release.
- BUG/MAJOR: mux-h2: Handle HEADERS frames received after a RST_STREAM
frame
- BUG/MAJOR: mux_h2: Don't consume more payload than received for
skipped frames
- BUG/MEDIUM: checks: make sure the connection is ready before trying
to recv